The Operational Readiness Assessment (ORA) would need to answer the question:
Do we have all the necessary contracts concluded and signed?

The necessary contracts can be:

• Client Contract(s)
• Subcontractor Contract(s)
• Operational Level Agreement(s) (OLAs)
• Additional Specific Contract(s)
• Rights To Use Contract(s) and other proof of the Rights To Use.

Preferably all contracts are signed before Service Commencement. However, not having all OLAs signed at Service Commencement date will often not become a showstopper. OLAs are operational type of documents that will probably be updated during the first months of Service Run anyway. The practice of executing the continuous service delivery will probably lead to the discovery of additional elements to add to the OLA.

Signing the Additional Specific Contract for taking over a project of the Client or the incumbent might also be postponed until after Service Commencement. Capgemini should take care of course that it does not take over the project or start executing part of the related work before the contract is signed.

Having not all templates for creating Additional Specific Contracts during service delivery in place could also be something Capgemini can live with for a certain amount of time after Service Commencement. This does not mean they should not be created of course.

The training about the contractual aspects should preferably be concluded before Service Commencement date. But, again, this should not be a showstopper for the Service Commencement.

The artifact Operational Readiness Assessment Log For Contracts is created and kept up-to-date to show (potential) show stoppers including the appropriate mitigation actions.